Update README.md#6
Conversation
Added a security policy document outlining supported versions and vulnerability reporting.
There was a problem hiding this comment.
┌──────────────────────────────────────────────────────────────────────────┐
│ ROADMAP · WHAT'S COMING filter: [all▾] │
├──────────────────────────────────────────────────────────────────────────┤
│ │
│ ◐ BUILDING Q1 2026 ◑ SHIPPING Q2 2026 ◯ ROADMAP Q3 2026 │
│ ┌───────────────────┐ ┌───────────────────┐ ┌────────────────┐ │
│ │ easyWorks │ │ NOI Command Ctr │ │ easyMonitor IoT│ │
│ │ Contractor Mktpl │ │ Bloomberg-style │ │ Switchee Nest │ │
│ │ £49/mo · 5 rails │ │ NOI · vacancy AI │ │ Hive · Octopus │ │
│ │ → Join waitlist │ │ → Preview shell │ │ → Join waitlist│ │
│ │ S3 · S5 │ │ S1 · S4 │ │ S2 · S6 │ │
│ └───────────────────┘ └───────────────────┘ └────────────────┘ │
│ ┌───────────────────┐ ┌───────────────────┐ ┌────────────────┐ │
│ │ Multilingual │ │ easyProtect │ │ Investor Pitch │ │
│ │ Tenant Portal │ │ Embedded Insrnce │ │ Live traction │ │
│ │ 30 langs · RTL │ │ Multi-underwriter │ │ Series Seed │ │
│ │ → Join waitlist │ │ → Join waitlist │ │ → Request acces│ │
│ │ S2 · S6 │ │ S3 · S5 │ │ S1 · S4 │ │
│ └───────────────────┘ └───────────────────┘ └────────────────┘ │
│ │
│ ↳ Tier 1 (Agentic AI · 5 agents) building now — see ⌘K → "agents" │
└──────────────────────────────────────────────────────────────────────────┘
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f91aeba5a7
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Use this section to tell people how to report a vulnerability. | ||
|
|
||
| Tell them where to go, how often they can expect to get an update on a | ||
| reported vulnerability, what to expect if the vulnerability is accepted or | ||
| declined, etc. |
There was a problem hiding this comment.
This section still contains placeholder instructions and does not provide any contact address, GitHub private vulnerability reporting guidance, or response process. In the scenario where someone finds a vulnerability and follows the repository's SECURITY.md, they have no actionable way to report it privately, so security reports may be delayed or disclosed through the wrong channel.
Useful? React with 👍 / 👎.
1 participant
docs/SECURITY-SETUP-GUIDE.md